home *** CD-ROM | disk | FTP | other *** search
Text File | 1990-11-29 | 3.5 KB | 96 lines | [TEXT/MPS ] |
- LOGistic
-
- (c) 1990 J.W. Sinteur
-
- LOGistic is shareware. To become a registered user, send $10 to
-
- J.W. Sinteur
- Strawinskypad 82
- 2324 DB Leiden
- The Netherlands
-
- There are NO limited versions of LOGistic. Unregistered users
- have the same functionality as registered users (but shame
- on them!), unlike the other piece of shareware on my name,
- HouseMaid.
-
- What LOGistic does:
-
- It takes your LOG files (like Tabby Log) and cuts out all
- unneeded crap. It's nice that most utilites like to tell
- you they started up perfectly at such and so hour and day,
- but it's not really interesting to a sysop whose BBS has been
- running stable for quite some time.
-
-
- How to set up LOGistic.
-
- Copy LOGistic to the folder in which your BBS program resides.
- Usually, this is the folder where all your BBS utilities can
- be found, like the BBS itself, TabbyNet, etc.
- LOGistic is Tabby event compatible. Put it anywhere in your
- event chain with Tabby Maint.
-
- BEFORE you do so, set up the following resources in LOGistic
- with ResEdit:
-
-
- STR resources:
-
- 1: BBS name. In this string, put the exact name (as it
- appears on disk) of your BBS application.
- 2: resulting log file. In this string, put the name of the
- file where you want the cut-down logt to appear. LOGistic
- copies the parts of the log file that are relevant to
- a new log file (it deletes all processed log files). I call
- this file 'Generic Log' (somewhat in the Tabby mind) myself.
- You can specify the full path to this file, so you can put
- it anywhere you like.
-
- STR# resources:
-
- LOGistic uses four STR# resources to find out on which files
- to do it's bit, and to find out what lines in a log file
- to keep. STR# 1 is connected in this way to STR# 3. In STR# 3
- you find the list of file names (complete pathnames) to the
- log files you wish to cut down in size with what I call the
- 'equal' protocol.
- All lines found in a file in the list in STR# 3 is compared
- to STR# 1. If any part of STR# 1 is found in the line, the line
- is copied to the Generic Log.
- This means you can use this type of cutting down for files
- which have lot's of different lines in them, and little
- error lines. Example: the Mansion BBS keeps a log for all
- user log-ins, like this:
- JOHN SINTEUR LEIDEN,NL 17:26:18 10-22-1989 3 3N
- JOHN SINTEUR LEIDEN,NL 17:03:44 10-28-1989 2 3N
-
- In STR# 1 you will find a list of words that are likely to
- occur in error messages (which you would like to keep of course)
-
-
- STR# 2 and STR# 4 are related in a similar fashion. STR# 4
- concains the files which will be treated by what I call
- the 'differ' protocol. Every line in a file from STR# 4
- that does NOT (in part) appear in STR# 2 will be copied
- to the Generic log. This is the perfect way to treat the
- Tabby Log.
- You most likely want to cut lines like
- 03/15/90 3:04:07 DeliverMail - Program Starting
- 03/15/90 3:04:20 DeliverMail - 1 E-Mail messages delivered
- 03/15/90 3:04:20 DeliverMail - 0 EchoMail messages delivered
- 03/15/90 3:04:21 DeliverMail - Program Ending
- from the log but keep lines like:
- 02/18/90 17:36:32 TabbyNet ERROR: XReceive - FidoNet mail receipt failed.
- 02/18/90 17:36:36 TabbyNet ERROR: ConnectChk - FidoMail receipt error.
- 02/18/90 17:36:37 TabbyNet terminating due to error.
-
- STR# 2 is set up in such a way. It will, at the moment, keep
- all error messages and lines with 'attempt to call' and
- 'disconnected' (to keep track of phone costs), but cut out
- most other lines. It is also set up to cut down on
- the file 'Mansion Log', so you might want to take a good
- look at STR# 2 before you use LOGistic.
-
-
- If you run into problems, contact me. Even if you didn't register.